- 3 minutes to read

Configure Microsoft BizTalk Server Logging Agent

Unlock centralized, future-proof logging for all your BizTalk Server environments with the Nodinite Logging Agent. On this page, you will:

  • ✅ Seamlessly replace BAM and modernize your logging strategy
  • ✅ Enable and manage logging across multiple BizTalk Server groups and versions
  • ✅ Configure, optimize, and remove logging with just a few clicks
  • ✅ Empower your team with robust monitoring and self-service configuration

You can add or remove logging for any BizTalk Server environment, whether you run legacy or new BizTalk instances. Nodinite lets you centralize, configure, and optimize logging for robust monitoring and seamless integration.

Prerequisites

Before you configure the Microsoft BizTalk Server Logging Agent, make sure you meet all BizTalk logging Prerequisites.

Configuration

Follow these steps to manage logging from one or more BizTalk Server Groups.

First, select the environment you want to manage using the Nodinite Update tool:
Manage BizTalk Log Agents
Example: The Manage BizTalk Log Agents button in Nodinite's Update tool.

Click the Add Log Agent Configuration button to add a new Microsoft BizTalk Server Logging Agent.
Add BizTalk Log Agent Button
Screenshot: Add a new BizTalk Log Agent configuration.

Log Agent Configuration

  1. Name – Assign a user-friendly name to the Log Agent.

    Tip

    Include the name and version of the target environment, for example, BizTalk 2016 PROD.

  2. Log Agent Value Id – Set a unique ID for this Log Agent Configuration. This value should never change once set!
  3. Description – Add a user-friendly description for this Log Agent Configuration.
  4. Log Agent - BizTalk settings – Check this option to mark the Log Agent as a BizTalk on-premise Log Agent Configuration.

Log Agent Source Part #1
Screenshot: Log Agent source configuration part 1.

BizTalk Databases

  1. BizTalkMgmtDb Server – Enter the SQL instance name hosting the BizTalk management database (linked server info from Nodinite SQL instance to BizTalk SQL Instance).
  2. BizTalkMgmtDb Name – Enter the BizTalk management database name.
  3. BizTalkDTADb Server – Enter the SQL instance name hosting the BizTalk tracking database (linked server info from Nodinite SQL instance to BizTalk SQL Instance).
  4. BizTalkDTADb Name – Enter the BizTalk tracking database name.

Log Agent Source Part #2
Screenshot: Log Agent source configuration part 2.

Tracking

  1. Polling Interval – Set the polling interval for the Logging Service. This is the time between attempts to fetch new logged data. Default: 30 seconds.
  2. Max number of Events to copy – Set the maximum number of events to fetch per run. Large numbers may impact performance. Default: 5000.
  3. Max number of Message/Context data rows to copy – Set the maximum number of payloads and context rows to fetch per run. Default: 500.

Log Agent Source Part #3
Screenshot: Log Agent source configuration part 3.

EndPoints

If you enable this option, Nodinite synchronizes all ports in BizTalk as Endpoints within the Repository Model.
Sync End Points Polling Interval – Set the poll period (in seconds) between synchronization attempts.
Include Endpoints Tracking status – Check this option if you use Microsoft BizTalk Server.

Log Agent Source Part #4
Screenshot: Log Agent source configuration part 4.

Remove

Remove the Nodinite BizTalk Server Log Agent configuration by clicking the Remove BizTalk Logging button.

Save

Click the Save button to save your configuration changes.

Note

Nodinite < 7.0 – You must restart the Nodinite Logging Service after making changes.
Nodinite >= 7.0 – Allow a few minutes for the initial synchronization with BizTalk Server to complete, then Logging becomes operational.

Next Step

Add or manage Log Agents
Administer Nodinite
Install the Nodinite Install and Update Tool
Replace BAM with Nodinite

BizTalk Prerequisites
Endpoints
Logging Service
Repository Model